build(objectql): give the package a test-layer tsc program and ledger its 242 errors - #14115

Fixes #13676

packages/objectql/tsconfig.json excluded **/*.test.ts, and the package's typecheck script was tsc --noEmit against that very config. So pnpm --filter @objectstack/objectql typecheck exiting 0 was a true sentence carrying no information about any of the package's 251 test files. This adopts the sibling-config route the repo already prescribes (the #5286 mechanism, generalised in #5449, and the route #12542 took for packages/rest).

The premise, re-verified before anything was written

Measured at 2a181174a6, workspace closure built first:

The premise held. engine-filter-array-lowering.test.ts — the negative pin required by maintainer ruling #13357 execution point 3, landed in #13673, proving a refused filter shape cannot reach the reference matcher — was in no tsc program at all.

What this changes

• packages/objectql/tsconfig.test.json (new) — module semantics matched to vitest (esnext / bundler / lib: ES2022) and rootDir widened to the package. ⛔ Strictness is untouched: strict, noUnusedLocals, noUnusedParameters, noImplicitReturns, noFallthroughCasesInSwitch all inherit from the root config.
• packages/objectql/package.json — typecheck now names the sibling via check:test-typecheck, plus gen:test-typecheck-debt. tsx added to devDependencies: it was not linked into this package, and the three onboarded siblings all declare it.
• packages/objectql/test-typecheck-debt.json (new, generated) — 44 files / 242 errors / 69 pinned signatures, exact and shrink-only.
• scripts/check-type-check-coverage.mjs — the @objectstack/objectql TEST_DEBT entry is deleted. The package graduated, and the gate itself demands the deletion.

The number this card was dispatched to produce

242 errors across 44 files, from a raw 251 under the inherited NodeNext semantics. The config tier removed is 9: TS2550 x8 (Array.prototype.at against a lib older than es2022) and TS1470 x1 (import.meta in a CJS program).

By code: TS2339 x115 · TS7006 x36 · TS2345 x34 · TS2749 x14 · TS2322 x14 · TS6133 x9 · TS18048 x8 · TS2353 x4 · 8 singletons.

Top files: engine.test.ts x102 · datasource-mapping.test.ts x17 · plugin.integration.test.ts x12 · hook-condition-fail-loud.test.ts x12 · registry.test.ts x10 · protocol-package-lifecycle.test.ts x8.

Every one of the 242 is pre-existing: this PR edits no test file, and each would have been reported on origin/main had this program ever existed. They are ledgered per file rather than repaired, which is what #12542 did for rest's 37 and #5286 for spec's 691. Paying them down belongs on its own card, as rest's does.

⛔ Not one any and not one @ts-expect-error was added anywhere to open this gate. Bulk-suppressing the residue is the exact shape this card exists to prevent — it turns a real gate into a phantom one.

⚠️ The negative pin: zero errors, and that zero is weak

src/engine-filter-array-lowering.test.ts reports 0 errors and therefore carries no ledger entry, so any error it ever gains is red on arrival. But read the zero correctly — it is not evidence the pin is type-checked:

• const driver: any — the recording driver, whose captured AST is the unreachability evidence.
• interface SeenRead { ast: any } — so lastWhere(), the expression the whole proof reads, is typed by nothing.
• 31 bare as any call sites, against the file's own header, which rejects "a bare as any" in favour of as unknown as EngineQueryOptions (asFilterArrayQuery, used 14 times).

A drifted IDataDriver signature would still not redden this file. Putting it in a program is the precondition for repairing that, not the repair; it is recorded separately and is deliberately not smuggled in here.

Verification

Run at 344681185a, workspace closure built first.

• pnpm --filter @objectstack/objectql typecheck — exit 0. Gate's own verdict: check:test-typecheck: OK — @objectstack/objectql's test layer compiles under packages/objectql/tsconfig.test.json; 44 file(s) / 242 error(s) / 69 pinned signature(s).
• pnpm --filter @objectstack/objectql exec vitest run --maxWorkers=2 — 251 test files passed, 4331 tests passed.
• pnpm check:type-check-coverage — exit 0. Test layer now reads 16 package(s) still hide their own tests / 695 files / 908 frozen errors, down from 17 / 946 / 1159.
• pnpm check:type-check-debt — exit 0. 27 ledger entr(ies) re-measured in 195.0s, 1217 raw tsc error(s) total, none above its recorded number. surplus: none.
• Full derived family (node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack, 34 commands): 32 exit 0, 1 already-green duplicate, 1 NOT MEASURED — check-test-completeness.mjs exits 3 without a CI test-run log, which its own text says to record as not measured rather than as a pass. Exit codes captured before any pipe.

Ablation — the ledger deletion is required, not cosmetic. Mutant taken byte-exact from a real commit (git checkout BASE -- scripts/check-type-check-coverage.mjs), confirmed on disk by hash (df3b0f68 to 84c4c608) and by the entry count going 0 to 1, then the gate run: exit 1, @objectstack/objectql: has a TEST_DEBT entry but has no test files -- it graduated; delete its entry from TEST_DEBT. Restore leg proven the same way and not merely trapped: on-disk hash back to df3b0f68, identical to the HEAD blob, with git diff HEAD empty.

No changeset: this publishes nothing from any package (files is dist / README.md / CHANGELOG.md, and neither new file is in it), matching PR #12570, the identical change for packages/rest, which merged under skip-changeset.

Generated by Claude Code

Generated by Claude Code